System, Method, and Computer Program Product for Dynamic Application Selection

ABSTRACT

A system, method, and computer program product for dynamic application selection for payment transactions determines identification data of an issuer institution associated with a portable financial device based at least partially on transaction data associated with at least one transaction at a merchant with the portable financial device. At least one electronic service application of a plurality of electronic service applications is determined based at least partially on the identification data of the issuer institution. Electronic service application data associated with the at least one electronic service application and stored in association with the issuer institution is accessed at a merchant system of the merchant. The at least one transaction is modified based at least partially on the electronic service application data associated with the at least one electronic service application. Authorization response message is received after communicating an authorization request message associated with the at least one modified transaction.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/641,835 filed Aug. 28, 2017, which is the U.S. national phase ofInternational Application No. PCT/US2017/048808 filed Aug. 28, 2017, thedisclosures of each of which are hereby incorporated by reference intheir entirety.

BACKGROUND 1. Technical Field

This disclosure relates generally to conducting a payment transactionand, in some non-limiting embodiments or aspects, to a method, system,and computer program product for dynamically selecting an applicationfor use in conducting a payment transaction.

2. Technical Considerations

Payment systems may include point-of-sale (POS) devices and portablefinancial devices to communicate and/or receive transaction data. Forexample, a portable financial device may communicate transaction data,such as a primary account number (PAN), to a POS device to conduct apayment transaction involving an account holder or user associated withthe portable financial device and a merchant associated with the POSdevice.

Conventional payment systems are typically standardized and haveidentical behavior regardless of the portable financial device and/oraccount holder or user conducting the transaction. Issuer institutionsand merchants cannot customize conventional POS devices to deliverunique cardholder experiences for payment transactions. For example,conventional POS devices cannot deliver value added services orapplications during a payment transaction according to an issuerinstitution and/or merchant associated with a payment transaction.Conventional POS devices cannot initiate and/or load a dynamicallyselected application from an issuer system and/or an externalthird-party system for use in conducting a payment transaction. Instead,conventional POS devices must always use a same predetermined paymenttransaction process to conduct payment transactions, and users mustmanually present an offer or coupon at the POS for the offer or couponto be applied to a payment transaction.

Therefore, there is a need in the art for payment systems to be able todeliver unique payment transaction experiences to account holders orusers, such as value-added services or applications customized accordingto issuer institution and/or merchant preferences, as well as theaccount holder or user conducting the transaction.

SUMMARY

Accordingly, provided are improved methods, systems, and computerprogram products for dynamically selecting an application for use inconducting a payment.

According to some non-limiting embodiments or aspects, provided is acomputer-implemented method for dynamic application selection forpayment transactions, the method comprising: determining, with at leastone processor, identification data of an issuer institution associatedwith a portable financial device based at least partially on transactiondata associated with at least one transaction at a merchant with theportable financial device; determining, with at least one processor, atleast one electronic service application of a plurality of electronicservice applications based at least partially on the identification dataof the issuer institution, wherein a plurality of electronic serviceapplication data associated with the plurality of electronic serviceapplications is stored in association with a plurality of issuinginstitutions at a merchant system of the merchant; accessing, with atleast one processor, electronic service application data of theplurality of electronic service application data associated with the atleast one electronic service application and stored in association withthe issuer institution at the merchant system of the merchant;modifying, with at least one processor, the at least one transactionbased at least partially on the electronic service application dataassociated with the at least one electronic service application;communicating, with at least one processor, an authorization requestmessage associated with the at least one modified transaction; andreceiving, with at least one processor, an authorization responsemessage after communicating the authorization request message.

According to some non-limiting embodiments or aspects, provided is asystem for dynamic application selection for payment transactions,comprising at least one computer including at least one processor, theat least one computer programmed and/or configured to: determineidentification data of an issuer institution associated with a portablefinancial device based at least partially on transaction data associatedwith at least one transaction at a merchant with the portable financialdevice; determine at least one electronic service application of aplurality of electronic service applications based at least partially onthe identification data of the issuer institution, wherein a pluralityof electronic service application data associated with the plurality ofelectronic service applications is stored in association with aplurality of issuing institutions at a merchant system of the merchant;access electronic service application data of the plurality ofelectronic service application data associated with the at least oneelectronic service application and stored in association with the issuerinstitution at the merchant system of the merchant; modify the at leastone transaction based at least partially on the electronic serviceapplication data associated with the at least one electronic serviceapplication; communicate an authorization request message associatedwith the at least one modified transaction; and receive an authorizationresponse message after communicating the authorization request message.

According to some non-limiting embodiments or aspects, provided is acomputer program product for dynamic application selection for paymenttransactions, the computer program product comprising at least onenon-transitory computer-readable medium including program instructionsthat, when executed by at least one processor cause the at least oneprocessor to: determine identification data of an issuer institutionassociated with a portable financial device based at least partially ontransaction data associated with at least one transaction at a merchantwith the portable financial device; determine at least one electronicservice application of a plurality of electronic service applicationsbased at least partially on the identification data of the issuerinstitution, wherein a plurality of electronic service application dataassociated with the plurality of electronic service applications isstored in association with a plurality of issuing institutions at amerchant system of the merchant; access electronic service applicationdata of the plurality of electronic service application data associatedwith the at least one electronic service application and stored inassociation with the issuer institution at the merchant system of themerchant; modify the at least one transaction based at least partiallyon the electronic service application data associated with the at leastone electronic service application; communicate an authorization requestmessage associated with the at least one modified transaction; andreceive an authorization response message after communicating theauthorization request message.

Further non-limiting embodiments or aspects are set forth in thefollowing numbered clauses:

Clause 1. A computer-implemented method for dynamic applicationselection for payment transactions, the method comprising: determining,with at least one processor, identification data of an issuerinstitution associated with a portable financial device based at leastpartially on transaction data associated with at least one transactionat a merchant with the portable financial device; determining, with atleast one processor, at least one electronic service application of aplurality of electronic service applications based at least partially onthe identification data of the issuer institution, wherein a pluralityof electronic service application data associated with the plurality ofelectronic service applications is stored in association with aplurality of issuing institutions at a merchant system of the merchant;accessing, with at least one processor, electronic service applicationdata of the plurality of electronic service application data associatedwith the at least one electronic service application and stored inassociation with the issuer institution at the merchant system of themerchant; modifying, with at least one processor, the at least onetransaction based at least partially on the electronic serviceapplication data associated with the at least one electronic serviceapplication; communicating, with at least one processor, anauthorization request message associated with the at least one modifiedtransaction; and receiving, with at least one processor, anauthorization response message after communicating the authorizationrequest message.

Clause 2. The computer-implemented method of clause 1, furthercomprising: receiving, with at least one processor, acceptance data thatindicates acceptance of the at least one electronic service application;and modifying, with at least one processor, the at least one transactionin response to the acceptance data.

Clause 3. The computer-implemented method of clauses 1 or 2, wherein theplurality of electronic service application data is stored on at leastone of the following: a Point-of-Sale (POS) device of the merchantsystem, a backend system of the merchant system, or any combinationthereof.

Clause 4. The computer-implemented method of any of clauses 1-3, furthercomprising: determining, with at least one processor, the at least oneelectronic service application of the plurality of electronic serviceapplications based at least partially on at least one rule and/oridentification data of the merchant.

Clause 5. The computer-implemented method of any of clauses 1-4, furthercomprising: associating, with at least one processor, the plurality ofelectronic service applications with a plurality of issuer institutionsbefore determining the identification data of the issuer institution,wherein the at least one electronic service application is associatedwith the issuer institution.

Clause 6. The computer-implemented method of any of clauses 1-5, whereinthe issuer institution is associated with two or more electronic serviceapplications of the plurality of electronic service applications, themethod further comprising: based at least partially on theidentification data of the issuer institution, determining, with atleast one processor, a subset of the two or more electronic serviceapplications as the at least one electronic service application.

Clause 7. The computer-implemented method of any of clauses 1-6, furthercomprising: determining, with at least one processor, the subset of thetwo or more electronic service applications based at least partially onat least one of the following: : a transaction amount of the at leastone transaction, a transaction date and/or time of the at least onetransaction, a location of the at least one transaction or merchant, acurrency of the at least one transaction, a transaction data category ofthe at least one transaction, a type of the portable financial device,or any combination thereof.

Clause 8. The computer-implemented method of any of clauses 1-7, furthercomprising: determining a ranking of the plurality of electronic serviceapplications based at least partially on at least one electronic serviceapplication ranking rule; and displaying, or causing the display of, theranking of the plurality of electronic service applications.

Clause 9. The computer-implemented method of any of clauses 1-8, furthercomprising: receiving, with at least one processor, the transaction dataassociated with the at least one transaction at the merchant with theportable financial device, wherein the transaction data comprisesportable financial device data associated with the portable financialdevice.

Clause 10. The computer-implemented method of any of clauses 1-9,wherein the portable financial device data comprises an accountidentifier.

Clause 11. The computer-implemented method of any of clauses 1-10,further comprising: communicating the portable financial device dataassociated with the portable financial device in response to receivingthe transaction data associated with the at least one transaction; andreceiving the identification data of the issuer institution aftercommunicating the portable financial device data.

Clause 12. The computer-implemented method of any of clauses 1-11,wherein determining the at least one electronic service applicationcomprises determining the at least one electronic service application inresponse to determining the identification data of the issuerinstitution associated with the portable financial device.

Clause 13. The computer-implemented method of any of clauses 1-12,wherein determining the identification data of the issuer institutionassociated with the portable financial device comprises determining aname of the issuer institution based on the portable financial devicedata included in the transaction data associated with the at least onetransaction.

Clause 14. The computer-implemented method of any of clauses 1-13,wherein the identification data of the issuer institution comprises atleast one of the following: a Bank Identification Number (BIN), a rangeof BINs, an Issuer Identification Number (IIN), a range of IINs, or anycombination thereof.

Clause 15. The computer-implemented method of any of clauses 1-14,wherein the authorization request message includes the electronicservice application data associated with the at least one electronicservice application, and wherein the electronic service application dataincludes data associated with at least one of the following: ane-commerce marketplace application, a rewards program applicationassociated with the portable financial device, a merchant applicationassociated with the merchant, an issuer application associated with theissuer institution, or any combination thereof.

Clause 16. The computer-implemented method of any of clauses 1-15,wherein the authorization request message includes the electronicservice application data associated with the at least one electronicservice application, and wherein the electronic service application dataincludes data associated with at least one of the following: offer dataassociated with an offer for a repayment plan based on a transactionamount of the at least one transaction; offer data associated with anoffer for a redemption offer for the merchant; offer data associatedwith an offer for a merchant loyalty program; or any combinationthereof.

Clause 17. The computer-implemented method of any of clauses 1-16,wherein the authorization request message includes the electronicservice application data associated with the at least one electronicservice application, and wherein the electronic service application dataincludes data associated with at least one of the following: repaymentplan data associated with a repayment plan based on a transaction amountof the at least one transaction; redemption offer data associated with aredemption offer for the merchant; program data associated with merchantloyalty program; program data associated with a reward program of theissuer institution associated with the portable financial device; or anycombination thereof.

Clause 18. The computer-implemented method of any of clauses 1-17,further comprising: determining transaction amount data of the at leastone transaction; determining whether the transaction amount datasatisfies a threshold transaction amount value, wherein determining theat least one electronic service application of the plurality ofelectronic service applications comprises: determining the at least oneelectronic service application of the plurality of electronic serviceapplications in response to determining that the transaction amount datasatisfies the threshold transaction amount value.

Clause 19. The computer-implemented method of any of clauses 1-18,wherein the plurality of electronic service application data comprisesApplication Programming Interface (API) information associated with theplurality of electronic service applications, the method furthercomprising: initiating, or causing the initiation of, with at least oneprocessor, at least one API call to at least one external computingsystem associated with the at least one electronic service applicationbased at least partially on the electronic service application dataassociated with the at least one electronic service application.

Clause 20. The computer-implemented method of any of clauses 1-19,further comprising: displaying, or causing the display of, with at leastone processor, at least a portion of the electronic service applicationdata associated with the at least one electronic service application ata display device in response to determining the at least one electronicservice application.

Clause 21. The computer-implemented method of any of clauses 1-20,wherein modifying the at least one transaction comprises at least one ofthe following: reducing a transaction amount of the at least onetransaction; dividing the transaction amount of the at least onetransaction into a plurality of installment amounts; automaticallyenrolling, or causing the enrollment of, a customer associated with theportable financial device in an incentive program, automaticallytransmitting, or causing the transmission of, a benefit to a user deviceof the customer; automatically crediting, or causing the crediting of, amerchant loyalty account of the customer; or any combination thereof.

Clause 22. The computer-implemented method of any of clauses 1-21,further comprising: conducting the at least one transaction using acloud-based Point-of-Sale (POS) system.

Clause 23. A system for dynamic application selection for paymenttransactions, comprising at least one computer including at least oneprocessor, the at least computer programmed and/or configured to:determine identification data of an issuer institution associated with aportable financial device based at least partially on transaction dataassociated with at least one transaction at a merchant with the portablefinancial device; determine at least one electronic service applicationof a plurality of electronic service applications based at leastpartially on the identification data of the issuer institution, whereina plurality of electronic service application data associated with theplurality of electronic service applications is stored in associationwith a plurality of issuing institutions at a merchant system of themerchant; access electronic service application data of the plurality ofelectronic service application data associated with the at least oneelectronic service application and stored in association with the issuerinstitution at the merchant system of the merchant; modify the at leastone transaction based at least partially on the electronic serviceapplication data associated with the at least one electronic serviceapplication; communicate an authorization request message associatedwith the at least one modified transaction; and receive an authorizationresponse message after communicating the authorization request message.

Clause 24. The system of clause 23, wherein the at least one computer isprogramed and/or configured to receive acceptance data that indicatesacceptance of the at least one electronic service application; andmodify the at least one transaction in response to the acceptance data.

Clause 25. The system of clauses 23 or 24, wherein the at least onecomputer is programmed and/or configured to determine the at least oneelectronic service application of the plurality of electronic serviceapplications based at least partially on at least one of the following:a transaction amount of the at least one transaction, a transaction dateand/or time of the at least one transaction, a location of the at leastone transaction or merchant, a currency of the at least one transaction,a transaction data category of the at least one transaction, a type ofthe portable financial device, or any combination thereof.

Clause 26. The system of any of clauses 23-25, wherein the at least onecomputer is programmed and/or configured to determine the at least oneelectronic service application of the plurality of electronic serviceapplications based at least partially on at least one rule and/oridentification data of the merchant.

Clause 27. The system of any of clauses 23-26, wherein the plurality ofelectronic service application data is stored on at least one of thefollowing: a Point-of-Sale (POS) device of the merchant, a backendsystem of the merchant, or any combination thereof.

Clause 28. The system of any of clauses 23-27, wherein the issuerinstitution is associated with two or more electronic serviceapplications of the plurality of electronic service applications, andwherein the at least one computer is programmed and/or configured todetermine a subset of the two or more electronic service applications asthe at least one electronic service application based at least partiallyon the identification data of the issuer institution.

Clause 29. The system of any of clauses 23-28, wherein the at least onecomputer is programmed and/or configured to determine the subset of thetwo or more electronic service applications based at least partially onat least one of the following: a transaction amount of the at least onetransaction, a transaction date and/or time of the at least onetransaction, a location of the at least one transaction or merchant, acurrency of the at least one transaction, a transaction data category ofthe at least one transaction, a type of the portable financial device,or any combination thereof.

Clause 30. The system of any of clauses 23-29, wherein the at least onecomputer is programmed and/or configured to: determine a ranking of theplurality of electronic service applications based at least partially onat least one electronic service application ranking rule; and display,or cause the display of, the ranking of the plurality of electronicservice applications.

Clause 31. The system of any of clauses 23-30, wherein the at least onecomputer is programmed and/or configured to receive the transaction dataassociated with the at least one transaction at the merchant with theportable financial device, wherein the transaction data comprisesportable financial device data associated with the portable financialdevice.

Clause 32. The system of any of clauses 23-31, wherein the portablefinancial device data comprises an account identifier.

Clause 33. The system of any of clauses 23-32, wherein the at least onecomputer is programmed and/or configured to: communicate the portablefinancial device data associated in response to receiving thetransaction data associated with the at least one transaction; andreceive the identification data of the issuer institution aftercommunicating the portable financial device data.

Clause 34. The system of any of clauses 23-33, wherein the at least onecomputer is programmed and/or configured to determine the at least oneelectronic service application in response to determination of theidentification data of the issuer institution associated with theportable financial device.

Clause 35. The system of any of clauses 23-34, wherein the at least onecomputer is programmed and/or configured to determine a name of theissuer institution based on the portable financial device data includedin the transaction data associated with the at least one transaction.

Clause 36. The system of any of clauses 23-35, wherein theidentification data of the issuer institution comprises at least one ofthe following: a Bank Identification Number (BIN), a range of BINs, anIssuer Identification Number (IIN), a range of IINs, or any combinationthereof.

Clause 37. The system of any of clauses 23-36, wherein the authorizationrequest message includes the electronic service application dataassociated with the at least one electronic service application, andwherein the electronic service application data includes data associatedwith at least one of the following: an e-commerce marketplaceapplication, a rewards program application associated with the portablefinancial device, a merchant application associated with the merchant,an issuer application associated with the issuer institution, or anycombination thereof.

Clause 38. The system of any of clauses 23-37, wherein the authorizationrequest message includes the electronic service application dataassociated with the at least one electronic service application, andwherein the electronic service application data includes data associatedwith at least one of the following: offer data associated with an offerfor a repayment plan based on a transaction amount of the at least onetransaction; offer data associated with an offer for a redemption offerfor the merchant; offer data associated with an offer for a merchantloyalty program; or any combination thereof.

Clause 39. The system of any of clauses 23-38, wherein the authorizationrequest message includes the electronic service application dataassociated with the at least one electronic service application, andwherein the electronic service application data includes data associatedwith at least one of the following: repayment plan data associated witha repayment plan based on a transaction amount of the at least onetransaction; redemption offer data associated with a redemption offerfor the merchant; program data associated with merchant loyalty program;program data associated with a reward program of the issuer institutionassociated with the portable financial device; or any combinationthereof.

Clause 40. The system of any of clauses 23-39, wherein the at least onecomputer is programmed and/or configured to: determine transactionamount data of the at least one transaction; determine whether thetransaction amount data satisfies a threshold transaction amount value;and determine the at least one electronic service application of theplurality of electronic service applications in response to adetermination that the transaction amount data satisfies the thresholdtransaction amount value.

Clause 41. The system of any of clauses 23-40, wherein the electronicservice application data comprises Application Programming Interface(API) information associated with the plurality of electronic serviceapplications, and wherein the at least one computer is programmed and/orconfigured to: initiate, or causing the initiation of, at least one APIcall to at least one external computing system associated with the atleast one electronic service application based at least partially on theelectronic service application data associated with the at least oneelectronic service application.

Clause 42. The system of any of clauses 23-41, wherein the at least onecomputer is programmed and/or configured to display, or cause thedisplay of, at least a portion of the electronic service applicationdata associated with the at least one electronic service application ata display device in response to determining the at least one electronicservice application.

Clause 43. The system of any of clauses 23-42, wherein the at least onecomputer comprises a cloud-based Point-of-Sale (POS) system.

Clause 44. A computer program product for dynamic application selectionfor payment transactions, the computer program product comprising atleast one non-transitory computer-readable medium including programinstructions that, when executed by at least one processor cause the atleast one processor to: determine identification data of an issuerinstitution associated with a portable financial device based at leastpartially on transaction data associated with at least one transactionat a merchant with the portable financial device; determine at least oneelectronic service application of a plurality of electronic serviceapplications based at least partially on the identification data of theissuer institution, wherein a plurality of electronic serviceapplication data associated with the plurality of electronic serviceapplications is stored in association with a plurality of issuinginstitutions at a merchant system of the merchant; access electronicservice application data of the plurality of electronic serviceapplication data associated with the at least one electronic serviceapplication and stored in association with the issuer institution at themerchant system of the merchant; modify the at least one transactionbased at least partially on the electronic service application dataassociated with the at least one electronic service application;communicate an authorization request message associated with the atleast one modified transaction; and receive an authorization responsemessage after communicating the authorization request message.

These and other features and characteristics of the present disclosure,as well as the methods of operation and functions of the relatedelements of structures and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the disclosure. Asused in the specification and the claims, the singular form of “a,”“an,” and “the” include plural referents unless the context clearlydictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional advantages and details of the disclosure are explained ingreater detail below with reference to the exemplary embodiments thatare illustrated in the accompanying schematic figures, in which:

FIG. 1 is a diagram of some non-limiting embodiments or aspects of anenvironment in which systems, devices, products, apparatus, and/ormethods, described herein, may be implemented according to theprinciples of the present disclosure;

FIG. 2 is a diagram of some non-limiting embodiments or aspects ofcomponents of one or more devices of FIG. 1;

FIG. 3 is a flowchart of some non-limiting embodiments or aspects of aprocess for dynamic application selection for payment transactionsaccording to the principles of the present disclosure;

FIG. 4 is a diagram of an implementation of some non-limitingembodiments or aspects of the process shown in FIG. 3;

FIG. 5 is a diagram of an implementation of some non-limitingembodiments or aspects of the process shown in FIG. 3; and

FIG. 6 is a diagram of an implementation of some non-limitingembodiments or aspects of the process shown in FIG. 3.

DETAILED DESCRIPTION

For purposes of the description hereinafter, the terms “end,” “upper,”“lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,”“lateral,” “longitudinal,” and derivatives thereof shall relate to thedisclosure as it is oriented in the drawing figures. However, it is tobe understood that the disclosure may assume various alternativevariations and step sequences, except where expressly specified to thecontrary. It is also to be understood that the specific devices andprocesses illustrated in the attached drawings, and described in thefollowing specification, are simply exemplary embodiments or aspects ofthe disclosure. Hence, specific dimensions and other physicalcharacteristics related to the embodiments or aspects of the embodimentsdisclosed herein are not to be considered as limiting unless otherwiseindicated.

No aspect, component, element, structure, act, step, function,instruction, and/or the like used herein should be construed as criticalor essential unless explicitly described as such. Also, as used herein,the articles “a” and “an” are intended to include one or more items, andmay be used interchangeably with “one or more” and “at least one.”Furthermore, as used herein, the term “set” is intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated and unrelated items, etc.) and may be used interchangeably with“one or more” or “at least one.” Where only one item is intended, theterm “one” or similar language is used. Also, as used herein, the terms“has,” “have,” “having,” or the like are intended to be open-endedterms. Further, the phrase “based on” is intended to mean “based atleast in partially on” unless explicitly stated otherwise.

As used herein, the terms “communication” and “communicate” may refer tothe reception, receipt, transmission, transfer, provision, and/or thelike, of information (e.g., data, signals, messages, instructions,commands, and/or the like). For one unit (e.g., a device, a system, acomponent of a device or system, combinations thereof, and/or the like)to be in communication with another unit means that the one unit is ableto directly or indirectly receive information from and/or transmitinformation to the other unit. This may refer to a direct or indirectconnection (e.g., a direct communication connection, an indirectcommunication connection, and/or the like) that is wired and/or wirelessin nature. Additionally, two units may be in communication with eachother even though the information transmitted may be modified,processed, relayed, and/or routed between the first and second unit. Forexample, a first unit may be in communication with a second unit eventhough the first unit passively receives information and does notactively transmit information to the second unit. As another example, afirst unit may be in communication with a second unit if at least oneintermediary unit (e.g., a third unit located between the first unit andthe second unit) processes information received from the first unit andcommunicates the processed information to the second unit. In somenon-limiting embodiments, a message may refer to a network packet (e.g.,a data packet, and/or the like) that includes data. It will beappreciated that numerous other arrangements are possible.

As used herein, the term “transaction service provider” may refer to anentity that receives transaction authorization requests from merchantsor other entities and provides guarantees of payment, in some casesthrough an agreement between the transaction service provider and theissuer institution. In some non-limiting embodiments, a transactionservice provider may include a credit card company, a debit cardcompany, and/or the like. As used herein, the term “transaction serviceprovider system” may also refer to one or more computer systems operatedby or on behalf of a transaction service provider, such as a transactionprocessing server executing one or more software applications. Atransaction processing server may include one or more processors and, insome non-limiting embodiments, may be operated by or on behalf of atransaction service provider.

As used herein, the terms “issuer institution,” “portable financialdevice issuer,” “issuer,” or “issuer bank” may refer to one or moreentities that provide accounts to customers for conducting transactions(e.g., payment transactions), such as initiating credit and/or debitpayments. For example, an issuer institution may provide an accountidentifier, such as a primary account number (PAN), to a customer thatuniquely identifies one or more accounts associated with that customer.The account identifier may be embodied on a portable financial device,such as a physical financial instrument, e.g., a payment card, and/ormay be electronic and used for electronic payments. The terms “issuerinstitution” and “issuer institution system” may also refer to one ormore computer systems operated by or on behalf of an issuer institution,such as a server computer executing one or more software applications.For example, an issuer institution system may include one or moreauthorization servers for authorizing a transaction.

As used herein, the term “acquirer” may refer to an entity licensed bythe transaction service provider and approved by the transaction serviceprovider to originate transactions (e.g., payment transactions) using aportable financial device associated with the transaction serviceprovider. As used herein, the term “acquirer system” may also refer toone or more computer systems, computer devices, and/or the like operatedby or on behalf of an acquirer. The transactions the acquirer mayoriginate may include payment transactions (e.g., purchases, originalcredit transactions (OCTs), account funding transactions (AFTs), and/orthe like). In some non-limiting embodiments, the acquirer may beauthorized by the transaction service provider to assign merchant orservice providers to originate transactions using a portable financialdevice of the transaction service provider. The acquirer may contractwith payment facilitators to enable the payment facilitators to sponsormerchants. The acquirer may monitor compliance of the paymentfacilitators in accordance with regulations of the transaction serviceprovider. The acquirer may conduct due diligence of the paymentfacilitators and ensure proper due diligence occurs before signing asponsored merchant. The acquirer may be liable for all transactionservice provider programs that the acquirer operates or sponsors. Theacquirer may be responsible for the acts of the acquirer's paymentfacilitators, merchants that are sponsored by an acquirer's paymentfacilitator, and/or the like. In some non-limiting embodiments, anacquirer may be a financial institution, such as a bank.

As used herein, the term “account identifier” may include one or morePANs, tokens, or other identifiers associated with a customer account.The term “token” may refer to an identifier that is used as a substituteor replacement identifier for an original account identifier, such as aPAN. Account identifiers may be alphanumeric or any combination ofcharacters and/or symbols. Tokens may be associated with a PAN or otheroriginal account identifier in one or more databases such that they canbe used to conduct a transaction without directly using the originalaccount identifier. In some examples, an original account identifier,such as a PAN, may be associated with a plurality of tokens fordifferent individuals or purposes. An issuer institution may beassociated with a bank identification number (BIN) or other uniqueidentifier that uniquely identifies it among other issuer institutions.

As used herein, the term “merchant” may refer to an individual or entitythat provides goods and/or services, or access to goods and/or services,to customers based on a transaction, such as a payment transaction. Theterm “merchant” or “merchant system” may also refer to one or morecomputer systems operated by or on behalf of a merchant, such as aserver computer executing one or more software applications. A“point-of-sale (POS) system,” as used herein, may refer to one or morecomputers and/or peripheral devices used by a merchant to engage inpayment transactions with customers, including one or more card readers,near-field communication (NFC) receivers, RFID receivers, and/or othercontactless transceivers or receivers, contact-based receivers, paymentterminals, computers, servers, input devices, and/or other like devicesthat can be used to initiate a payment transaction.

As used herein, a “point-of-sale (POS) device” may refer to one or moredevices, which may be used by a merchant to initiate transactions (e.g.,a payment transaction), engage in transactions, and/or processtransactions. For example, a POS device may include one or morecomputers, peripheral devices, card readers, near-field communication(NFC) receivers, radio frequency identification (RFID) receivers, and/orother contactless transceivers or receivers, contact-based receivers,payment terminals, computers, servers, input devices, and/or the like.

As used herein, the term “computing device” may refer to one or moreelectronic devices that are configured to directly or indirectlycommunicate with or over one or more networks. The computing device maybe a mobile device. As used herein, the term “mobile device” may referto one or more portable electronic devices configured to communicatewith one or more networks. As an example, a mobile device may include acellular phone (e.g., a smartphone or standard cellular phone), aportable computer (e.g., a tablet computer, a laptop computer, etc.), awearable device (e.g., a watch, pair of glasses, lens, clothing, and/orthe like), a personal digital assistant (PDA), and/or other likedevices. The computing device may not be a mobile device, such as adesktop computer. Furthermore, the term “computer” may refer to anycomputing device that includes the necessary components to receive,process, and output data, and normally includes a display, a processor,a memory, an input device, and a network interface. The term “clientdevice,” as used herein, refers to any electronic device that isconfigured to communicate with one or more servers or remote devicesand/or systems. A client device may include a mobile device, anetwork-enabled appliance (e.g., a network-enabled television,refrigerator, thermostat, and/or the like), a computer, a POS system,and/or any other device or system capable of communicating with anetwork.

As used herein, the terms “client” and “client device” may refer to oneor more client-side devices or systems (e.g., remote from a transactionservice provider) used to initiate or facilitate a transaction (e.g., apayment transaction). As an example, a “client device” may refer to oneor more POS devices used by a merchant, one or more acquirer hostcomputers used by an acquirer, one or more mobile devices used by auser, and/or the like. In some non-limiting embodiments, a client devicemay be an electronic device configured to communicate with one or morenetworks and initiate or facilitate transactions. For example, a clientdevice may include one or more computers, portable computers, tabletcomputers, cellular phones, wearable devices (e.g., watches, glasses,lenses, clothing, and/or the like), PDAs, and/or the like. Moreover, a“client” may also refer to an entity (e.g., a merchant, an acquirer,and/or the like) that owns, utilizes, and/or operates a client devicefor initiating transactions (e.g., for initiating transactions with atransaction service provider).

As used herein, the term “server” may refer to one or more computingdevices (e.g., processors, storage devices, similar computer components,and/or the like) that communicate with client devices and/or othercomputing devices over a network (e.g., a public network, the Internet,a private network, and/or the like) and, in some examples, facilitatecommunication among other servers and/or client devices. It will beappreciated that various other arrangements are possible. As usedherein, the term “system” may refer to one or more computing devices orcombinations of computing devices (e.g., processors, servers, clientdevices, software applications, components of such, and/or the like).Reference to “a device,” “a server,” “a processor,” and/or the like, asused herein, may refer to a previously-recited device, server, orprocessor that is recited as performing a previous step or function, adifferent server or processor, and/or a combination of servers and/orprocessors. For example, as used in the specification and the claims, afirst server or a first processor that is recited as performing a firststep or a first function may refer to the same or different server orthe same or different processor recited as performing a second step or asecond function.

As used herein, the terms “electronic wallet,” “electronic wallet mobileapplication,” and “digital wallet” may refer to one or more electronicdevices and/or one or more software applications configured to initiateand/or conduct transactions (e.g., payment transactions, electronicpayment transactions, and/or the like). For example, an electronicwallet may include a user device (e.g., a mobile device) executing anapplication program and server-side software and/or databases formaintaining and providing transaction data to the user device. As usedherein, the term “electronic wallet provider” may include an entity thatprovides and/or maintains an electronic wallet and/or an electronicwallet mobile application for a user (e.g., a customer). Examples of anelectronic wallet provider include, but are not limited to, GoogleWallet™, Android Pay®, Apple Pay®, and Samsung Pay®. In somenon-limiting examples, a financial institution (e.g., an issuerinstitution) may be an electronic wallet provider. As used herein, theterm “electronic wallet provider system” may refer to one or morecomputer systems, computer devices, servers, groups of servers, and/orthe like operated by or on behalf of an electronic wallet provider.

As used herein, the term “portable financial device” may refer to apayment device, an electronic payment device, a payment card (e.g., acredit or debit card), a gift card, a smartcard, smart media, a payrollcard, a healthcare card, a wrist band, a machine-readable mediumcontaining account information, a keychain device or fob, an RFIDtransponder, a retailer discount or loyalty card, a cellular phone, anelectronic wallet mobile application, a personal digital assistant(PDA), a pager, a security card, a computer, an access card, a wirelessterminal, a transponder, and/or the like. In some non-limitingembodiments, the portable financial device may include volatile ornon-volatile memory to store information (e.g., an account identifier, aname of the account holder, and/or the like).

As used herein, the term “payment gateway” may refer to an entity and/ora payment processing system operated by or on behalf of such an entity(e.g., a merchant service provider, a payment service provider, apayment facilitator, a payment facilitator that contracts with anacquirer, a payment aggregator, and/or the like), which provides paymentservices (e.g., transaction service provider payment services, paymentprocessing services, and/or the like) to one or more merchants. Thepayment services may be associated with the use of portable financialdevices managed by a transaction service provider. As used herein, theterm “payment gateway system” may refer to one or more computer systems,computer devices, servers, groups of servers, and/or the like, operatedby or on behalf of a payment gateway and/or to a payment gateway itself.The term “payment gateway mobile application” may refer to one or moreelectronic devices and/or one or more software applications configuredto provide payment services for transactions (e.g., paymenttransactions, electronic payment transactions, and/or the like).

As used herein, the term “application” or “application programinterface” (API) refers to computer code, a set of rules, or other datasorted on a computer-readable medium that may be executed by a processorto facilitate interaction between software components, such as aclient-side front-end and/or server-side back-end for receiving datafrom the client. An “interface” refers to a generated display, such asone or more graphical user interfaces (GUIs) with which a user mayinteract, either directly or indirectly (e.g., through a keyboard,mouse, etc.).

As used herein, the term “electronic service application” refers to anyapplication or API that may be executed by a processor to facilitateconducting or processing a payment transaction.

Non-limiting embodiments or aspects of the present disclosure aredirected to systems, methods, and computer program products fordynamically selecting an electronic service application for use inconducting or processing a payment transaction. Non-limiting embodimentsor aspects of the present disclosure allow for initiating and/or loadinga dynamically selected application from an issuer system and/or anexternal third-party system for use in conducting a payment transactionat a merchant POS device. These features enable a POS device to delivervalue added services or applications and unique payment transactionexperiences to customers during a payment transaction according topreferences of an issuer institution associated with a paymenttransaction. For example, a transaction can be modified duringconducting or processing of the transaction according to an electronicservice application that was dynamically selected based on transactiondata of the transaction. This enables a merchant or acquirer to uniquelyconfigure transaction processing according to an issuer institutionassociated with the transaction before completing the transaction. Thesefeatures also enable a transaction to be modified, for example, with anoffer or coupon, without requiring a user to manually present the offeror coupon at the POS for the offer or coupon to be applied to a paymenttransaction.

Non-limiting embodiments or aspects of the present disclosure mayinclude a computer-implemented method that comprises issuing at leastone API call to at least one remote or external computing systemassociated with the at least one electronic service application. In thisway, processor and network resources may be reduced as compared toconventional POS devices. These features further enable POS devices thatprovide customized transaction experiences when compared to conventionalPOS devices that are standardized and have identical behavior regardlessof the portable financial device and/or account holder or userconducting the transaction. Moreover, a an offer or coupon associatedwith a third party other than the merchant system can still be appliedto a payment transaction even if a user does not manually present theoffer or coupon at the POS by issuing an API call to a remote orexternal computing system associated with the third party and providingat least one electronic service application that can be used to applythe offer or coupon to the payment transaction.

Referring to FIG. 1, some non-limiting embodiments or aspects of anenvironment 100 in which systems, devices, products, apparatus, and/ormethods, as described herein, may be implemented is shown. As shown inFIG. 1, environment 100 may include transaction service provider system102, issuer system 104, user device 106, merchant system 108, acquirersystem 114, service application provider system 116, and network 120. Asfurther shown in FIG. 1, merchant system 108 may include point-of-sale(POS) device 110 and backend system 112.

Transaction service provider system 102 may include one or more devicescapable of receiving information from and/or communicating informationto issuer system 104, user device 106, merchant system 108, acquirersystem 114, and/or service application provider system 116, via network120. For example, transaction service provider system 102 may includeone or more computing devices, a server, a group of servers, and/or thelike. In some non-limiting embodiments or aspects, transaction serviceprovider system 102 may be associated with an entity (e.g., atransaction service provider) that operates a credit card network andthat processes payments for credit accounts, debit accounts, creditcards, debit cards, and/or the like.

Issuer system 104 may include one or more devices capable of receivinginformation from and/or communicating information to transaction serviceprovider system 102, user device 106, merchant system 108, acquirersystem 114, and/or service application provider system 116, via network120. For example, issuer system 104 may include one or more computingdevices, a server, a group of servers, and/or the like. In somenon-limiting embodiments or aspects, the issuer system 104 may beassociated with an issuer institution as described herein. In somenon-limiting embodiments or aspects, issuer system 104 may be associatedwith an issuer institution that issued a credit account, debit account,credit card, debit card, and/or the like to a user associated with userdevice 106.

User device 106 may include one or more devices capable of receivinginformation from and/or communicating information to transaction serviceprovider system 102, issuer system 104, merchant system 108, acquirersystem 114, and/or service application provider system 116, via network120. For example, user device 106 may include a client device, acomputer device, a desktop computer, a mobile device, and/or the like.In some non-limiting embodiments or aspects, a mobile device may includeone or more portable electronic devices configured to communicate withone or more other electronic devices via a network (e.g., network 120).For example, a mobile device may include a cellular phone (e.g., asmartphone or standard cellular phone), a portable computer (e.g., atablet computer, a laptop computer, etc.), a wearable device (e.g., awatch, pair of glasses, lens, clothing, and/or the like), a personaldigital assistant (PDA), and/or other like devices. In some non-limitingembodiments or aspects, user device 106 may be capable of receivinginformation (e.g., from merchant system 108) via a short range wirelesscommunication connection (e.g., an NFC communication connection, aRadio-frequency identification (RFID) communication connection, aBluetooth® communication connection, and/or the like), and/orcommunicating information (e.g., to merchant system 108) via a shortrange wireless communication connection.

Merchant system 108 may include one or more devices capable of receivinginformation from and/or communicating information to transaction serviceprovider system 102, issuer system 104, user device 106, acquirer system114, and/or service application provider system 116, via network 120.For example, merchant system 108 may include a computing device, aserver, a group of servers, a client device, a group of client devicesand/or the like. In some non-limiting embodiments or aspects, merchantsystem 108 may be associated with a merchant as described herein. Insome non-limiting embodiments or aspects, merchant system 108 mayinclude one or more user devices 106. For example, merchant system 108may include user device 106 that allows a merchant associated withmerchant system 108 to receive information from and/or communicateinformation to transaction service provider system 102, issuer system104, user device 106, acquirer system 114, and/or service applicationprovider system 116, via network 120.

In some non-limiting embodiments or aspects, merchant system 108 may becapable of being used by a merchant to initiate, engage in, and/orconduct a payment transaction with a user (e.g., a customer, a consumer,and/or the like), which may be associated with user device 106. Forexample, merchant system 108 may include one or more computers, servers,input devices, payment terminals, magnetic stripe card readers, chipcard readers, contactless transceivers, contactless receivers, NFCreceivers, RFID receivers, contact-based receivers, and/or other and/orthe like. In some non-limiting embodiments or aspects, merchant system108 may include a device capable of receiving information from userdevice 106 via a short range wireless communication connection (e.g., acommunication connection that uses NFC protocol, a communicationconnection that uses Radio-frequency identification (RFID), acommunication connection that uses a Bluetooth® wireless technologystandard, and/or the like), and/or communicating information to userdevice 106 via a short range wireless communication connection.

Merchant system 108 may include POS device 110 and backend system 112.In some non-limiting embodiments or aspects, POS device 110 may includea POS terminal (e.g., a POS terminal located at a location of amerchant) and/or an electronic device that performs the functions of aPOS terminal. In some non-limiting embodiments or aspects, backendsystem 112 may include a computing device, a server, a group of servers,and/or the like. In some non-limiting embodiments or aspects, POS device110 and/or backend system 112 may be capable of receiving informationfrom and/or communicating information to transaction service providersystem 102, issuer system 104, user device 106, acquirer system 114,and/or service application provider system 116, via network 120. In somenon-limiting embodiments or aspects, POS device 110 and backend system112 may be capable of receiving information from and/or communicatinginformation to each other. For example, POS device 110 and backendsystem 112 may be capable of receiving information from and/orcommunicating information to each other via a network (e.g., network120). In some non-limiting embodiments or aspects, backend system 112may be separate from merchant system 108. For example, backend system112 may be associated with transaction service provider system 102,issuer system 104, acquirer system 114, and/or service applicationprovider system 116, and/or backend system 112 may include a cloud-basedPOS system.

Acquirer system 114 may include one or more devices capable of receivinginformation from and/or communicating information to transaction serviceprovider system 102, issuer system 104, user device 106, merchant system108, and/or service application provider system 116, via network 120.For example, acquirer system 114 may include a computing device, aserver, a group of servers, and/or the like. In some non-limitingembodiments or aspects, acquirer system 114 may be associated with anacquirer as described herein.

Service application provider system 116 may include one or more systemsthat include one or more devices capable of receiving information fromand/or communicating information to transaction service provider system102, issuer system 104, user device 106, merchant system 108, acquirersystem 114, via network 120. For example, service application providersystem 116 may include one or more computing devices, a server, a groupof servers, and/or the like. In some non-limiting embodiments oraspects, service application provider system 116 may be associated withan entity that provides one or more programs, such as e-commercemarketplace programs, discount programs, financing programs, incentiveprograms, coupon programs, rewards programs, and the like, that can beused in conducting or processing a payment transaction. For example, aservice application provider may be an entity, such as Groupon, andprovide one or more electronic service applications via serviceapplication provider system 116 to merchant system 108 for use inconducting or processing a payment transaction as described herein. Insome non-limiting embodiments or aspects, service application providersystem 116 may comprise transaction service provider system 102, issuersystem 104, merchant system 108, acquirer system 114, an electronicwallet provider system associated with an electronic wallet provider asdescribed herein, and/or a payment gateway system associated with apayment gateway as described herein, that provides one or moreelectronic service applications via service application provider system116 to merchant system 108 for use in conducting or processing a paymenttransaction as described herein.

Network 120 may include one or more wired and/or wireless networks. Forexample, network 120 may include a cellular network (e.g., a long-termevolution (LTE) network, a third generation (3G) network, a fourthgeneration (4G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the public switched telephone network (PSTN)),a private network (e.g., a private network associated with a transactionservice provider), an ad hoc network, an intranet, the Internet, a fiberoptic-based network, a cloud computing network, and/or the like, and/ora combination of these or other types of networks.

The number and arrangement of systems, devices, and/or networks shown inFIG. 1 are provided as an example. There may be additional systems,devices, and/or networks; fewer systems, devices, and/or networks;different systems, devices, and/or networks; and/or differently arrangedsystems, devices, and/or networks than those shown in FIG. 1.Furthermore, two or more systems or devices shown in FIG. 1 may beimplemented within a single system or device, or a single system ordevice shown in FIG. 1 may be implemented as multiple, distributedsystems or devices. Additionally, or alternatively, a set of systems(e.g., one or more systems) or a set of devices (e.g., one or moredevices) of environment 100 may perform one or more functions describedas being performed by another set of systems or another set of devicesof environment 100. For example, transaction service provider system102, issuer system 104, user device 106, acquirer system 114, serviceapplication provider system 116, an electronic wallet provider system,and/or a payment gateway system may be capable of being used toinitiate, engage in, and/or conduct a payment transaction with a user(e.g., a customer, a consumer, and/or the like), as described hereinwith respect to merchant system 108.

A customer or user may be a holder of a portable financial device (e.g.,an account holder) and use that portable financial device associatedwith a transaction service provider and issued by an issuer which mayhave issuer system 104 operated by or on behalf of the issuer. Thecustomer or user may use the portable financial device to initiatetransactions with merchant system 108 having POS device 110. In somenon-limiting embodiments or aspects, the customer or user may purchasegoods or services from the merchant using the portable financial deviceand the merchant system 108 to guarantee payment of the goods orservices.

The merchant system 108 may communicate with the transaction serviceprovider system 102 to initiate further processing of a transactionbetween the merchant system 108 and the customer or user. This may be inthe form of a transaction authorization request to request furtherprocessing of a transaction initiated with the portable financialdevice. The merchant system 108 may communicate transaction data to thetransaction service provider system 102. The transaction data mayinclude transaction parameters associated with transactions initiatedwith the portable financial device of the customer or user. Non-limitingexamples of transaction parameters include: primary account number(PAN), Bank Identification Number (BIN), a range of BINs, IssuerIdentification Number (IIN), a range of IINs, transaction amount,transaction date and time, conversion rate of currency, merchant type,acquiring institution country, PAN country, response code, merchantname/location, type of currency, and the like. Response code may referto a successful approval/completion of a transaction, denial becausecard reported as lost or stolen, do not honor, partial approval, VIPapproval (VIP program), amount exceeds maximum, insufficient funds,incorrect PIN, suspected fraud, activity amount exceeded, allowablenumber of PIN-entry tries exceeded, and the like. Other relevantresponse codes from the credit card issuer response codes may beincluded as the response code, where relevant. Further, it will beappreciated that these transaction parameters associated withtransactions of the user may be communicated to the transaction serviceprovider system 102, and may be stored in a transaction service providerdatabase, for example, as transaction data in association with thecustomer or user.

In some non-limiting embodiments or aspects, the transaction data mayinclude the following transaction data categories: travel andentertainment transactions, retail transactions, dining transactions,“everyday” spending transactions, or any combination thereof. Forexample, the transaction data may define for a customer or userproportions of transactions in travel and entertainment transactions,retail transactions, dining transactions, and everyday spendingtransactions. Travel and entertainment category transactions may includetransactions related to airlines, lodging, vehicle rental, entertainmentand travel services, and the like. Retail category transactions mayinclude transactions related to apparel and accessories, departmentstores, discount stores, general retail goods, electronics and homeimprovement stores, and the like. Dining category transactions mayinclude transactions related to restaurants and quick servicerestaurants, and the like. Everyday spending category transactions mayinclude transactions related to food and groceries, fuel,transportation, drugstores and pharmacies, and the like. Travel andentertainment transactions, retail transactions, and dining transactionsmay be defined as discretionary spending. Everyday spending transactionsmay be defined as non-discretionary spending. Any other metric may beincluded that is determined to be relevant for defining the purchasingor spending behavior of an account holder or user 100. In somenon-limiting embodiments or aspects, the transaction data may includemore narrowly defined transaction data categories, such as transactiondata categories defined based at least partially on Merchant CategoryClassification (MCC) codes. MCC is used to classify a merchant by thetype of goods or services the merchant provides. MCC codes can beassigned by merchant type, (e.g., one for hotels, one for office supplystores, one for coffee merchants, etc.), or by merchant name (e.g., 3000for United Airlines).

Referring now to FIG. 2, FIG. 2 is a diagram of example components of adevice 200. Device 200 may correspond to transaction service providersystem 102, issuer system 104, user device 106, merchant system 108, POSdevice 110, backend system 112, acquirer system 114, service applicationprovider system 116, and/or one or more devices of transaction serviceprovider system 102, issuer system 104, user device 106, merchant system108, backend system 112, acquirer system 114, and/or service applicationprovider system 116. In some non-limiting embodiments or aspects,transaction service provider system 102, issuer system 104, user device106, merchant system 108, POS device 110, backend system 112, acquirersystem 114, and/or service application provider system 116, may includeat least one device 200 and/or at least one component of device 200. Asshown in FIG. 2, device 200 may include bus 202, processor 204, memory206, storage component 208, input component 210, output component 212,and communication interface 214.

Bus 202 may include a component that permits communication among thecomponents of device 200. In some non-limiting embodiments or aspects,processor 204 may be implemented in hardware, firmware, or a combinationof hardware and software. For example, processor 204 may include aprocessor (e.g., a central processing unit (CPU), a graphics processingunit (GPU), an accelerated processing unit (APU), etc.), amicroprocessor, a digital signal processor (DSP), and/or any processingcomponent (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.), and/or the like,which can be programmed to perform a function. Memory 206 may include arandom-access memory (RAM), a read only memory (ROM), and/or anothertype of dynamic or static storage device (e.g., a flash memory, amagnetic memory, an optical memory, etc.) that stores information and/orinstructions for use by processor 204.

Storage component 208 may store information and/or software related tothe operation and use of device 200. For example, storage component 208may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 210 may include a component that permits device 200 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 210may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 212 may include a component that provides outputinformation from device 200 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 214 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 200 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 214 may permit device 200to receive information from another device and/or provide information toanother device. For example, communication interface 214 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 200 may perform one or more processes described herein. Device200 may perform these processes based on processor 204 executingsoftware instructions stored by a computer-readable medium, such asmemory 206 and/or storage component 208. A computer-readable medium(e.g., a non-transitory computer-readable medium) is defined herein as anon-transitory memory device. A memory device includes memory spacelocated inside of a single physical storage device or memory spacespread across multiple physical storage devices.

Software instructions may be read into memory 206 and/or storagecomponent 208 from another computer-readable medium or from anotherdevice via communication interface 214. When executed, softwareinstructions stored in memory 206 and/or storage component 208 may causeprocessor 204 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, embodiments or aspects describedherein are not limited to any specific combination of hardware circuitryand software.

The number and arrangement of components shown in FIG. 2 are provided asan example. In some non-limiting embodiments or aspects, device 200 mayinclude additional components, fewer components, different components,or differently arranged components than those shown in FIG. 2.Additionally, or alternatively, a set of components (e.g., one or morecomponents) of device 200 may perform one or more functions described asbeing performed by another set of components of device 200.

Referring now to FIG. 3, a process 300 is shown for dynamic applicationselection for payment transactions. In some non-limiting embodiments oraspects, one or more of the steps of process 300 may be performed (e.g.,completely, partially, etc.) by merchant system 108 including POS device110 and/or backend system 112. In some non-limiting embodiments oraspects, one or more of the steps of process 300 may be performed (e.g.,completely, partially, etc.) by another system, another device, anothergroup of systems, or another group of devices, separate from orincluding merchant system 108, such as transaction service providersystem 102 (e.g., one or more devices of transaction service providersystem 102), issuer system 104 (e.g., one or more devices of issuersystem 104), user device 106, merchant system 108 (e.g., one or moredevices of merchant system 108), acquirer system 114 (e.g., one or moredevices of acquirer system 114), and/or service application providersystem 116 (e.g., one or more devices of service application providersystem 116). In some non-limiting embodiments or aspects, one or more ofthe steps of process 300 may be performed (e.g., completely, partially,etc.) by POS device 110, which may be a computing device, such as atablet computer, that executes cloud-based POS software, such as Poynt,ThumbzUp, and the like, that provide a merchant interface on POS device110 and deliver cloud-based APIs to the POS device 110.

As shown in FIG. 3, process 300 includes a step 302 of determining, withat least one processor, identification data of an issuer institutionassociated with a portable financial device based at least partially ontransaction data associated with at least one transaction at a merchantwith the portable financial device. At a step 304, at least oneprocessor determines at least one electronic service application of aplurality of electronic service applications based at least partially onthe identification data of the issuer institution, wherein a pluralityof electronic service application data associated with the plurality ofelectronic service applications is stored in association with aplurality of issuing institutions at a merchant system of the merchant.At a step 306, at least one processor accesses electronic serviceapplication data of the plurality of electronic service application dataassociated with the at least one electronic service application andstored in association with the issuer institution at the merchant systemof the merchant. At a step 308, at least one processor modifies the atleast one transaction based at least partially on the electronic serviceapplication data associated with the at least one electronic serviceapplication. At a step 310, at least one processor communicates anauthorization request message associated with the at least one modifiedtransaction. At a step 312, at least one processor receives anauthorization response message after communicating the authorizationrequest message.

With continued reference to FIG. 3, step 302 may include receiving, withat least one processor, the transaction data associated with the atleast one transaction at the merchant with the portable financialdevice, wherein the transaction data comprises portable financial devicedata associated with the portable financial device. For example, acustomer or user initiates a financial transaction using a portablefinancial device associated with a transaction service provider and anissuer institution. The transaction may be a financial transaction withmerchant system 108. The customer or user provides portable financialdevice data from his/her portable financial device to the merchantsystem 108 to conduct or complete a financial transaction in exchangefor goods or services offered by the identified merchant. For example,POS device 110 of merchant system 108 may receive the portable financialdevice data from the portable financial device of the customer or user,(e.g., from a credit card, a debit card, a mobile device 106, etc. ofthe customer or user that provides the portable financial device data tothe POS device 110). In some non-limiting embodiments or aspects, thetransaction can be conducted or processed using a cloud-based POSsystem. For example, the POS device 110 may comprise a user device 106or other computing device, such as a mobile device or tablet computer,that transmits the portable financial device data to a remote server orsystem that conducts or processes the transaction remotely from the POSdevice 110. The portable financial device data can include an accountidentifier, (e.g., 16-digit PAN), a Bank Identification Number (BIN), arange of BINs, an Issuer Identification Number (IIN), a range of IINs,or any combination thereof. However, the portable financial device datais not limited thereto and may include any data associated with theportable financial device and/or account holder or user of the portablefinancial device.

In some non-limiting embodiments or aspects, the identification data ofthe issuer institution comprises at least one of the following: a BankIdentification Number (BIN), a range of BINs, an Issuer IdentificationNumber (IIN), a range of IINs, or any combination thereof. In step 302,determining the identification data of the issuer institution associatedwith the portable financial device of the customer may comprisedetermining a name of the issuer institution based on the portablefinancial device data included in the transaction data associated withthe at least one transaction. For example, the merchant system 108 candetermine the identification data of the issuer institution byidentifying a PAN, BIN, IIN, a range of BINs, and/or a range of IINs, inthe portable financial device data, and determine the issuer institutionassociated with that PAN, BIN, IIN, range of BINs, or range of IINs. Insome non-limiting embodiments or aspects, the merchant system 108 canaccess a look-up table that associates known issuer institutions withPANs, BINs, IINs, ranges of BINs, and/or ranges of IINs, to determinethe issuer institution. In some non-limiting embodiments or aspects, atleast one processor, in response to receiving the transaction dataassociated with the at least one transaction, can communicate theportable financial device data associated with the customer, and receivethe identification data of the issuer institution after communicatingthe portable financial device data. For example, the merchant system 108can communicate the portable financial device data to the transactionservice provider system 102 and/or the issuer system 104, and receivefrom the transaction service provider system 102 and/or the issuersystem 104 the identification data, such as a name of the issuerinstitution associated with a PAN, BIN, IIN, a range of BINs, and/or arange of IINs included in the portable financial device data.

With continued reference to FIG. 3, step 304 may include associating,with at least one processor, the plurality of electronic serviceapplications with a plurality of issuer institutions before determiningthe identification data of the issuer institution, wherein the at leastone electronic service application is associated with the issuerinstitution. For example, the merchant system 108 can store and/oraccess the identification data of the plurality of issuer institutionsin association with one or more of the plurality of electronic serviceapplications at POS device 110, backend system 112, a merchant systemdatabase, and/or a remote system, such as a cloud-based POS systemserver, transaction service provider system 102, issuer system 104,acquirer system 114, and/or service application provider system 116. Insome non-limiting embodiments or aspects, an issuer institution can beassociated with two or more electronic service applications of theplurality of electronic service applications.

In some non-limiting embodiments or aspects, merchant system 108 canstore and/or access the plurality of electronic service applicationsand/or electronic service application data associated with the pluralityof electronic service applications with at least one of the following:POS device 110, backend system 112, a merchant system database, a remotesystem, such as a cloud-based POS system server, transaction serviceprovider system 102, issuer system 104, acquirer system 114, and/orservice application provider system 116, or any combination thereof. Insome non-limiting embodiments or aspects, the at least one electronicservice application may be cloud-based, for example, accessed over thenetwork 120 by the merchant system 108 at backend system 112,transaction service provider system 102, issuer system 104, acquirersystem 114, and/or service application provider system 116. For example,the merchant system 108 may store in a memory electronic serviceapplication data associated with the plurality of electronic serviceapplications, wherein the electronic service application data comprisesApplication Programming Interface (API) information associated with eachof the plurality of electronic service applications, and initiate, orcause the initiation of, at least one API call to at least one remote orexternal computing system associated with the at least one electronicservice application based at least partially on the electronic serviceapplication data. POS device 110 may initiate an API call to backendsystem 112, transaction service provider system 102, issuer system 104,acquirer system 114, or service application provider system 116, andbackend system 112, transaction service provider system 102, issuersystem 104 acquirer system 114, or service application provider system116 may provide access to the electronic service application and/orelectronic service application data associated with the electronicservice application, such as interfaces, user prompts, and/or results ofprocessing the at least one transaction with the electronic serviceapplication at the remote or external computing system, to the POSdevice 110 in response to the API call. The POS device 110 may be acomputing device, such as a tablet computer, that executes cloud-basedPOS software, such as Poynt, ThumbzUp, and the like, that provide amerchant interface on the POS device 110 and deliver cloud-based APIs tothe POS device 110. In some non-limiting embodiments or aspects, themerchant system 108 may store in a local memory, such as on POS device110, all or a portion of the plurality of electronic serviceapplications. For example, the merchant system 108 may store all or aportion of the electronic service application data associated with theat least one electronic service application and process the at least onetransaction locally with the at least one electronic serviceapplication.

With continued reference to FIG. 3, step 304 may include determining theat least one electronic service application in response to determiningthe identification data of the issuer institution associated with theportable financial device of the customer. For example, the merchantsystem 108 can determine the issuer institution associated with the PAN,BIN, IIN, range of BINs, range of IINs, and/or issuer institution namedetermined from the transaction data, and determine at least oneelectronic service application that is associated with the determinedissuer institution. In some non-limiting embodiments or aspects, themerchant system 108 can access a look-up table that associates theplurality of electronic service applications and/or electronic serviceapplication data associated therewith with known issuer institutions,and select at least one electronic service application that isassociated with the determined issuer institution in the look-up tablefor use in conducting or processing the at least one transaction.

In some non-limiting embodiments or aspects, the at least one electronicservice application of the plurality of electronic service applicationsis determined based at least partially on at least one of the following:the transaction data, identification data of the issuer institution,identification data of the merchant, at least one rule, or anycombination thereof. For example, the merchant system 108 can determineat least one electronic service application that is associated with thedetermined issuer institution and a merchant associated with themerchant system 108 for use in conducting or processing the transaction.In some non-limiting embodiments or aspects, the merchant system 108 maynot determine at least one electronic service application or determine adefault electronic service application for use in conducting orprocessing the transaction if there is no electronic service applicationof the plurality of electronic service applications associated with thedetermined issuer institution and the merchant associated with themerchant system 108. For example, a merchant may choose to configure aPOS device 110 to determine electronic service applications for use inconducting or processing transactions associated with portable financialdevices of certain issuer institutions, while using default or standardtransaction processing, e.g., transaction processing that does notmodify the transaction, to conduct transactions associated with portablefinancial devices of other issuer institutions.

In some non-limiting embodiments or aspects, at least one electronicservice application of the plurality of electronic service applicationsmay be associated with at least one rule, and the merchant system 108can determine an electronic service application that is associated withthe determined issuer institution as the at least one electronic serviceapplication for use in conducting or processing the at least onetransaction if transaction data associated with the at least onetransaction satisfies the at least one rule associated with thatelectronic service application. The at least one rule may define atleast one of the following requirements with respect to a transactionfor an electronic service application to be determined for use inconducting or processing the transaction: transaction amount,transaction date and/or time, transaction or merchant location,transaction currency, transaction data category, type of portablefinancial device, or any combination thereof. For example, the merchantsystem 108 may determine transaction amount data of the at least onetransaction, determine whether the transaction amount data satisfies athreshold transaction amount value, and determine the at least oneelectronic service application of the plurality of electronic serviceapplications in response to determining that the transaction amount datasatisfies the threshold transaction amount value. For example, anelectronic service application that modifies a transaction by reducing arequired or requested payment amount for completing the transaction, orthat offers to divide the required or requested payment into multipleinstallment payments, may only be used in conducting or processing atransaction if an original required or requested amount for completingthe transaction is above a threshold amount, such as an amount over$1000.

In some non-limiting embodiments or aspects, if the at least one rule isnot satisfied, e.g., if a transaction amount does not meet or exceed athreshold transaction amount, the merchant system 108 may conduct orprocess the transaction without determining an electronic serviceapplication for use in the transaction, or determine a default orstandard electronic service application for use in the transaction,e.g., standard processing by the POS device 110 that attempts toauthorize the transaction with the transaction service provider system102 and/or the issuer system 104 without modifying the transaction withan electronic service application.

In some non-limiting embodiments or aspects, an issuer institution canbe associated with two or more electronic service applications of theplurality of electronic service applications, and at least one processorcan determine, based at least partially on one of the following: thetransaction data, the identification data of the issuer institution, theidentification data of the merchant, the at least one rule, or anycombination thereof, a subset of the two or more electronic serviceapplications as the at least one electronic service application. Forexample, the two or more electronic service applications may include twoor more of the following: one or more repayment plans based on atransaction amount of the at least one transaction; one or moreredemption offers for the merchant; one or more merchant loyaltyprograms; one or more reward programs of the issuer institutionassociated with the portable financial device; or any combinationthereof. The merchant system 108 may select a subset, such as anelectronic service application that provides a largest discount of twoor more electronic service applications that provide redemption offersfor the merchant, of the two or more electronic service applications foruse in conducting or processing the payment transaction. For example,the merchant system 108 may determine a ranking of the two or moreelectronic service applications based at least partially on at least oneelectronic service application ranking rule, e.g., the merchant system108 may determine ranking of the two or more electronic serviceapplications according to a discount available from each of the two ormore electronic service applications, such as a ranking from a largestdiscount to a smallest discount that can be applied to the at least onetransaction, and automatically select the at least one electronicservice application based on the ranking, e.g., select an electronicservice application of the two or more electronic service applicationsthat provides the greatest discount. However, non-limiting embodimentsor aspects are not limited thereto and two or more electronic serviceapplications associated with the same issuer institution can be rankedaccording to any one or more of the parameters of the transaction dataassociated with the at least one transaction.

With continued reference to FIG. 3, step 306 may include displaying, orcausing the display of, with at least one processor, at least a portionof the electronic service application data associated with the at leastone electronic service application at a display device in response todetermining the at least one electronic service application. Forexample, the POS device 110 of the merchant system 108, or the userdevice 106, may display to a customer or user an interface or promptthat requests authorization from the customer or user to conduct orprocess the at least one transaction with the at least one electronicservice application determined based on the identification data of theissuer institution. The interface or prompt may include electronicservice application data that explains an effect of conducting orprocessing the at least one transaction with the electronic serviceapplication, such as a modification of the at least one transaction or atarget action that will be initiated with respect to the customer oruser. The customer or user can input their authorization to the POSdevice 110, either directly or via user device 106, as acceptance datato indicate acceptance of the at least one electronic serviceapplication. In some non-limiting embodiments or aspects, the POS device110 may request that the customer or user select the at least oneelectronic service application from the two or more electronic serviceapplications. For example, the customer or user may be presented with anoption in the interface or prompt displayed by the POS device 110 tochoose between two or more different incentive programs to use inconducting or processing the at least one transaction.

In some non-limiting embodiments or aspects, the merchant system 108 maydetermine a ranking of the plurality of electronic service applicationsbased at least partially on at least one electronic service applicationranking rule and display, or cause the display of, the ranking of theplurality of electronic service applications. For example, the POSdevice 110 may display a list ranking available discounts, e.g., from alargest discount to a smallest discount, that can be applied to the atleast one transaction, and the customer or user can select via the POSdevice 110 the available discount and corresponding electronic serviceapplication that the customer or user wants to be used to conduct orprocess the at least one transaction, (e.g., the acceptance data mayindicate an acceptance of a specific electronic service application(s)of the plurality of electronic service applications). In somenon-limiting embodiments or aspects, the POS device 110 canautomatically select the at least one electronic service applicationbased on the ranking of the plurality of electronic service application.For example, the POS device 110 can automatically select a highestranked electronic service application, (e.g., that provides a largestdiscount), and apply that electronic service application to the at leastone transaction in response to acceptance data indicating acceptance ofthe automatically selected electronic service application by thecustomer or user.

With continued reference to FIG. 3, step 308 may include in response tothe acceptance data, modifying, with at least one processor, thetransaction data associated with the at least one transaction based atleast partially on the electronic service application data associatedwith the at least one electronic service application. An electronicservice application may include one or more rules or functions that canbe applied to the at least one transaction to modify the at least onetransaction. The merchant system 108 may apply one or more rules definedby electronic service application data associated with the at least oneelectronic service application to the transaction data of the at leastone transaction to modify the at least one transaction and/or thetransaction data associated therewith. The electronic serviceapplication data may include data associated with at least one of thefollowing: an e-commerce marketplace application, a rewards programapplication associated with the portable financial device, a merchantapplication associated with the merchant, an issuer applicationassociated with the issuer institution, or any combination thereof. Forexample, the electronic service application data may include dataassociated with at least one of the following: offer data associatedwith an offer for a repayment plan based on a transaction amount of theat least one transaction; offer data associated with an offer for aredemption offer for the merchant; offer data associated with an offerfor a merchant loyalty program; or any combination thereof. In somenon-limiting embodiments or aspects, the electronic service applicationdata includes data associated with at least one of the following:repayment plan data associated with a repayment plan based on atransaction amount of the at least one transaction; redemption offerdata associated with a redemption offer for the merchant; program dataassociated with merchant loyalty program; program data associated with areward program of the issuer institution associated with the portablefinancial device; or any combination thereof.

In some non-limiting embodiments or aspects, an electronic serviceapplication can be applied to the at least one transaction to apply acoupon to the at least one transaction. For example, merchant system 108can automatically process the at least one transaction based at leastpartially on at least one coupon associated with service applicationprovider system 116 that provides the electronic service application,(e.g., an electronic coupon from Groupon), and redeem the at least onecoupon in association with the at least one transaction to modify thetransaction data associated with the at least one transaction, e.g., tomodify a transaction amount of the at least one transaction.

In some non-limiting embodiments or aspects, an electronic serviceapplication can be applied to the at least one transaction to reduce atransaction amount required or requested for completing the transaction.A transaction amount of the at least one transaction may be reduced by apercentage amount based at least partially on an electronic serviceapplication used to conduct or process the transaction. For example, ifmerchant system 108 determines that a credit card associated with the atleast one transaction has an BIN associated with an issuer institutionthat provides an electronic service application that provides a discountto cardholders for using their card at that merchant, the merchantsystem 108 can discount the at least one transaction by applying theelectronic service application to the at least one transaction.

In some non-limiting embodiments or aspects, an electronic serviceapplication can be applied to the at least one transaction to split atransaction amount for the at least one transaction into a plurality ofinstallments or a payment plan, e.g., an initial payment and one or morelater payments, such as at 3, 6, and 9 months from the date of theinitial payment or initiation of the transaction. The electronic serviceapplication can automatically schedule the one or more later payments tobe automatically deducted from an account associated with the portablefinancial device associated with the transaction. For example, theelectronic service application can cause the merchant system 108, thetransaction service provider system 102, and/or the issuer system 104 toautomatically schedule, conduct and/or process sub-transactions for theone or more later payments at subsequently scheduled dates.

In some non-limiting embodiments or aspects, an electronic serviceapplication can modify the at least one transaction by automaticallyinitiating, or causing the initiation of, a target action with respectto a customer or user associated with the at least one transaction. Insome non-limiting embodiments or aspects, at least one processor mayautomatically credit a merchant loyalty account associated with thecustomer or user for a merchant loyalty program based at least partiallyon the at least one electronic service application. For example, themerchant system 108 may automatically credit the loyalty accountassociated with the customer or user with a discount, coupon, cash back,promotional item, sweepstakes, or any other incentive to the customer oruser by updating a merchant loyalty database in the merchant system 108.

In some non-limiting embodiments or aspects, at least one processor mayautomatically enroll a customer or user associated with the at least onetransaction in an incentive program based at least partially on the atleast one electronic service application. The target action may includethe at least one electronic service application causing merchant system108 to communicate with transaction service provider system 102, issuersystem 104, acquirer system 114, and/or service application providersystem 116 to cause transaction service provider system 102, issuersystem 104, acquirer system 114, and/or service application providersystem 116 to automatically enroll the customer or user in at least oneincentive program associated with the transaction service providersystem 102, issuer system 104, acquirer system 114, and/or serviceapplication provider system 116. The incentive program may include anyprogram that provides a benefit to the customer or user. The benefit maybe provided to the customer or user contingent on past, present, orcurrent use of their portable financial device(s). The benefit may be inthe form of a discount, coupon, cash back, promotional item,sweepstakes, or any other incentive to the customer or user. Thecustomer or user may be entered into one or multiple incentive programs.The at least one electronic service application used to conduct orprocess the transaction can automatically identify an incentiveprogram(s) into which the customer or user is automatically enrolled, orallow the customer or user to select an incentive program(s) into whichthe customer or user is automatically enrolled via POS device 110.

In some non-limiting embodiments or aspects, automatically enrolling acustomer or user in the incentive program(s) may cause a benefit to betransmitted to a user device 106 of the customer or user, such as butnot limited to a voucher in an electronic wallet application. In othernon-limiting embodiments or aspects, the at least one electronic serviceapplication can cause the merchant system 108, transaction serviceprovider system 102, issuer system 104, acquirer system 114, and/orservice application provider system 116 to generate and/or transmit atargeted communication to the user device 106 of the customer or user.The communication may include information regarding use of theirportable financial device, including the benefits of using the portablefinancial device at specific merchants and/or for specific types oftransactions. The communication may also include an offer to enter atleast one incentive program as described above. This communication maybe sent in combination with automatically enrolling the customer or userin an incentive program (e.g., a notification communication notifyingthe customer or user of enrollment in an incentive program). Thecommunication may be automatically generated and sent to the user device106 of the customer or user by the merchant system 108, transactionservice provider system 102, issuer system 104, acquirer system 114,and/or service application provider system 116. The communication maytake any communication form, including a web-based communication, anemail communication, a text message, a telephone call, a pushnotification, and/or an instant message. The customer or user mayrespond to the communication. A targeted offer may also include anyother action directed to incentivizing, educating, or encouraging acustomer or user to more frequently use their portable financial deviceat specific merchants and/or for specific types of transactions.

With continued reference to FIG. 3, in step 310, an authorizationrequest message may include the electronic service application dataassociated with the at least one electronic service application, thetransaction data, the modified transaction data, or any combinationthereof. The merchant system 108 can transmit an authorization requestmessage including the modified transaction data to transaction serviceprovider system 102, issuer system 104, acquirer system 114, and/orservice application provider system 116 so that the payment transactionmay be authorized, settled, and/or cleared. For example, if anelectronic service application applied to the at least one transactionreduces a transaction amount of the at least one transaction, theauthorization request message may include a request for authorization ofa net transaction amount, e.g., an original transaction amount less adiscount, such as a discount from a Groupon or other coupon, and aninstruction to bill the net amount. If an electronic service applicationapplied to the at least one transaction splits a total transactionamount of the at least one transaction into multiple installmentamounts, the authorization request message may include a request forauthorization of the total transaction amount and an instruction toinitially bill only an initial installment amount of the multipleinstallments. In some non-limiting embodiments or aspects, theauthorization request message may include request to schedule automaticbilling of the later installment amounts on a specific date(s).

In some non-limiting embodiments or aspects, an authorization requestmessage may include a request to enroll a customer or user associatedwith the at least one transaction in an incentive program associatedwith the merchant system 108, transaction service provider system 102,issuer system 104, acquirer system 114, and/or service applicationprovider system 116, and/or a request that the merchant system 108,transaction service provider system 102, issuer system 104, acquirersystem 114, and/or service application provider system 116 generateand/or transmit a targeted communication to the user device 106 of thecustomer or user, as described herein.

In some non-limiting embodiments or aspects, backend system 112 ofmerchant system 108 may generate the authorization request message. Forexample, backend system 112 may receive the modified transaction datafrom POS device 110 and backend system 112 may generate theauthorization request message associated with the at least one modifiedtransaction. In some non-limiting embodiments or aspects, POS device 110of merchant system 108 may generate the authorization request message.

With continued reference to FIG. 3, in step 312, an authorizationresponse message may include an indication that the payment transactionwas successfully completed (e.g., authorized, cleared, settled, and/orthe like) or not successfully completed (e.g., not authorized, notcleared, not settled, and/or the like). For example, the merchant system108 may receive an authorization response message in response to anauthorization request message. In some non-limiting embodiments, POSdevice 810 may display the indication that the payment transaction wassuccessfully completed or not successfully completed. In somenon-limiting embodiments or aspects, backend system 112 of merchantsystem 108 may receive the authorization response message. For example,backend system 112 may receive the authorization response message fromtransaction service provider system 102 and/or issuer system 104 andbackend system 112 may transmit the authorization response message toPOS device 110. In some non-limiting embodiments or aspects, POS device110 of merchant system 108 may directly receive the authorizationresponse message from the transaction service provider system 102 and/orissuer system 104.

FIG. 4 is a diagram of an overview of some non-limiting embodiments oraspects of an implementation 400 relating to process 300 shown in FIG.3. As shown in FIG. 4, implementation 400 may include a customer oruser, a POS device 410, transaction service provider system 402, and/orissuer system 404. In some non-limiting embodiments or aspects, POSdevice 410 may be the same as or similar to POS device 110 as describedabove, transaction service provider system 402 may be the same as orsimilar to transaction service provider system 102 as described above,and issuer system 404 may be the same as or similar to issuer system 104described above.

It is noted that implementation 400 is described primarily with respectto POS device 410 performing one or more functions referenced byreference numbers in FIG. 4; however, additionally, or alternatively, aremote system or server, such as backend server 112 of merchant system108 that communicates with POS device 410, or a cloud-based server of acloud-based POS system in which POS device 410 comprises a user device,such as a tablet computer, that communicates with the cloud-basedserver, may perform one or more functions referenced by the referencenumbers in FIG. 4.

As shown by reference number 420 in FIG. 4, POS device 410 may receiveportable financial device data including an account identifier for aportable financial device of the customer or user to conduct a paymenttransaction in exchange for goods or services offered by a merchantassociated with the POS device 410.

As shown by reference number 422 in FIG. 4, POS device 410 determines anissuer institution associated with the portable financial device. Forexample, the account identifier may include a BIN that uniquelyidentifies the issuer institution. As shown by reference number 424, POSdevice 410 determines if at least one electronic service application isassociated with the determined issuer institution. For example, the POSdevice 410 can use a look-up table to identify an electronic serviceapplication associated with the determined issuer institution. If thereis no electronic service application associated with the issuerinstitution, the POS device 410 may proceed directly to attempting toauthorize the payment transaction without modifying the paymenttransaction with an electronic service application.

In reference number 424, the POS device 410 may apply at least one ruleto transaction data associated with the transaction. The at least onerule may define at least one of the following requirements of thetransaction for the electronic service application to be determined foruse in conducting or processing the transaction: transaction amount,transaction date and time, transaction or merchant location, transactioncurrency, transaction data category, type of portable financial device,or any combination thereof. For example, a total transaction amountgreater than $1,000 may be required to use an electronic serviceapplication that converts a transaction amount of a transaction intomultiple monthly installment payments in conducting or processing thetransaction.

As shown in reference number 426, the POS device 410 provides aninterface or prompt that requests acceptance from the customer or userto conduct or process the transaction with the determined electronicservice application. For example, the POS device 410 may access or loadthe at least one electronic service application to prompt the customeror user to convert the transaction amount of the transaction into themultiple monthly installment payments. In some non-limiting embodimentsor aspects, as shown in reference number 428, the POS device 410provides the interface or prompt and/or receives the at least one ruleby issuing at least one API call to at least one remote or externalcomputing system associated with the at least one electronic serviceapplication, such as issuer system 404 associated with the determinedissuing institution that provides the electronic service application forconverting a transaction amount into multiple monthly installmentpayments. In some non-limiting embodiments or examples, the POS device410 provides the interface or prompt with a request for additionalinformation from the customer or user to configure application of theelectronic service application according to one or more userpreferences. For example, the POS device 410 can prompt the customer oruser to choose 3, 6, or 9-month installment payments for the electronicservice application for converting a transaction amount into multiplemonthly installment payments.

As shown in reference number 430, the POS device 410 receives acceptanceto conduct or process the transaction with the electronic serviceapplication and, if applicable, one or more user preferences, such as aselection of 3-month installment payments for an electronic serviceapplication for converting a transaction amount into multiple monthlyinstallment payments. If the POS device 410 does not receive acceptanceto conduct or process the transaction with the electronic serviceapplication, (e.g., the customer or user declines the acceptance requestor a timer after sending the acceptance request times out), the POSdevice 410 may proceed directly to attempting to authorize the paymenttransaction without modifying the payment transaction with theelectronic service application. However, non-limiting embodiments andaspects are not limited thereto, and application of some electronicservice applications may be performed automatically by the POS device410 without requesting and/or receiving acceptance from the customer oruser.

As shown in reference number 432, in response to theacceptance/preferences shown in reference number 430, the POS device 430modifies the transaction with the electronic service application. Forexample, the POS device 430 converts a transaction amount of thetransaction into an initial amount and one or more subsequent amounts,such as an initial amount of $500 dollar, a first subsequent amount of500 dollars to be billed at a date three months from the transactiondate, and a second subsequent amount of $500 to be billed at a date 6months from the transaction date.

As shown in reference number 434 the POS device 410 transmits anauthorization request message including the modified transaction dataand/or the electronic service application data to transaction serviceprovider system 402 and issuer system 404 so that the paymenttransaction may be authorized, settled, and/or cleared. As shown inreference number 436, in response to the authorization request messageas shown in reference number 434, the POS device 410 receives anauthorization response message that includes an indication that thepayment transaction was successfully completed (e.g., authorized,cleared, settled, and/or the like) or not successfully completed (e.g.,not authorized, not cleared, not settled, and/or the like). As shown inreference number 438, POS device 410 may display the indication that thepayment transaction was successfully completed or not successfullycompleted.

FIG. 5 is a diagram of an overview of some non-limiting embodiments oraspects of an implementation 500 relating to process 300 shown in FIG.3. As shown in FIG. 5, implementation 500 may include a customer oruser, a POS device 510, transaction service provider system 502, issuersystem 504, and service application provider system 516. In somenon-limiting embodiments or aspects, POS device 510 may be the same asor similar to POS device 110 as described above, transaction serviceprovider system 502 may the same as or similar to transaction serviceprovider system 102 as described above, issuer system 504 may be thesame as or similar to issuer system 104 described above, and serviceapplication provider system 516 may be the same as or similar to serviceapplication provider system 116.

It is noted that implementation 500 is described primarily with respectto POS device 510 performing one or more functions referenced byreference numbers in FIG. 5; however, additionally, or alternatively, aremote system or server, such as backend server 112 of merchant system108 that communicates with POS device 510, or a cloud-based server of acloud-based POS system in which POS device 510 comprises a user device,such as a tablet computer, that communicates with the cloud-basedserver, may perform one or more functions referenced by the referencenumbers in FIG. 5.

As shown by reference number 520 in FIG. 5, POS device 510 may receiveportable financial device data including an account identifier for aportable financial device of the customer or user to conduct a paymenttransaction in exchange for goods or services offered by a merchantassociated with the POS device 510.

As shown by reference number 522 in FIG. 5, POS device 510 determines anissuer institution associated with the portable financial device. Forexample, the account identifier may include a BIN that uniquelyidentifies the issuer institution. As shown by reference number 524, POSdevice 510 determines if at least one electronic service application isassociated with the determined issuer institution. For example, the POSdevice 510 can query a look-up table to identify an electronic serviceapplication associated with the determined issuer institution. If thereis no electronic service application associated with the issuerinstitution, the POS device 510 may proceed directly to attempting toauthorize the payment transaction without modifying the paymenttransaction with an electronic service application.

In reference number 524, the POS device 510 may apply at least one ruleto transaction data associated with the transaction. The at least onerule may define at least one of the following requirements of thetransaction for the electronic service application to be determined foruse in conducting or processing the transaction: transaction amount,transaction date and time, transaction or merchant location, transactioncurrency, transaction data category, type of portable financial device,or any combination thereof. For example, an electronic serviceapplication that reduces a transaction amount of a transaction, e.g., bya percentage amount, may require that the transaction include goods orservices in a particular transaction data category and/or a transactionamount above a threshold transaction amount.

As shown in reference number 526, the POS device 510 provides aninterface or prompt that requests acceptance from the customer or userto conduct or process the transaction with the determined electronicservice application. For example, the POS device 510 may access or loadthe at least one electronic service application to prompt the customeror user to reduce the transaction amount of the transaction. In somenon-limiting embodiments or aspects, as shown in reference number 528,the POS device 510 provides the interface or prompt and/or receives theat least one rule by issuing at least one API call to serviceapplication provider system 116 associated with the at least oneelectronic service application for converting a transaction amount intomultiple monthly installment payments. For example, service applicationprovider system 116 may be one or more computer systems operated by oron behalf of an e-commerce marketplace or discount provider, such asGroupon. In some non-limiting embodiments or examples, the POS device510 provides the interface or prompt with a request for additionalinformation from the customer or user to configure application of theelectronic service application according to one or more userpreferences. For example, the POS device 510 can prompt the customer oruser to choose between multiple different discount options for reducingthe transaction amount, or automatically select a discount option thatprovides a greatest discount for the customer or user.

As shown in reference number 530, the POS device 510 receives acceptanceto conduct or process the transaction with the electronic serviceapplication and, if applicable, one or more user preferences, such as aselection of discount for reducing a transaction amount. If the POSdevice 510 does not receive acceptance to conduct or process thetransaction with the electronic service application, e.g., the customeror user declines the request or a timer initiated after sending theacceptance request times out, the POS device 510 may proceed directly toattempting to authorize the payment transaction without modifying thepayment transaction with the electronic service application. However,non-limiting embodiments and aspects are not limited thereto, andapplication of some electronic service applications may be performedautomatically by the POS device 510 without requesting and/or receivingacceptance from the customer or user.

As shown in reference number 532, in response to theacceptance/preferences shown in reference number 530, the POS device 530modifies the transaction with the electronic service application. Forexample, the POS device 530 reduces a transaction amount of thetransaction from an initial or gross amount into a reduced or modifiedamount, e.g., an initial amount of $100 reduced by 30% results in areduced or modified amount of $70 to be billed to complete thetransaction.

As shown in reference number 534 the POS device 510 transmits anauthorization request message including the modified transaction dataand/or electronic service application data to transaction serviceprovider system 502 and issuer system 504 so that the paymenttransaction may be authorized, settled, and/or cleared. As shown inreference number 536, in response to the authorization request messageas shown in reference number 534, the POS device 510 receives anauthorization response message that includes an indication that thepayment transaction was successfully completed (e.g., authorized,cleared, settled, and/or the like) or not successfully completed (e.g.,not authorized, not cleared, not settled, and/or the like). As shown inreference number 538, POS device 510 may display the indication that thepayment transaction was successfully completed or not successfullycompleted.

FIG. 6 is a diagram of an overview of some non-limiting embodiments oraspects of an implementation 600 relating to process 300 shown in FIG.3. As shown in FIG. 6, implementation 600 may include a customer oruser, a user device 606, a POS device 610, transaction service providersystem 602, issuer system 604, and backend system 612. In somenon-limiting embodiments or aspects, user device 606 may be the same asor similar to user device 106 as described above, POS device 610 may bethe same as or similar to POS device 110 as described above, transactionservice provider system 602 may the same as or similar to transactionservice provider system 102 as described above, issuer system 604 may bethe same as or similar to issuer system 104 described above, serviceapplication provider system 616 may be the same as or similar to serviceapplication provider system 116 as described above, and backend system612 may be the same as or similar to backend system 112 as describedabove.

It is noted that implementation 600 is described primarily with respectto POS device 610 performing one or more functions referenced byreference numbers in FIG. 6; however, additionally, or alternatively, aremote system or server, such as backend server 612 that communicateswith POS device 610, or a cloud-based server of a cloud-based POS systemin which POS device 610 comprises a user device, such as a tabletcomputer, that communicates with the cloud-based server, may perform oneor more functions referenced by the reference numbers in FIG. 6.

As shown by reference numbers 620 in FIG. 6, POS device 610 may receiveportable financial device data including an account identifier for aportable financial device of the customer or user to conduct a paymenttransaction in exchange for goods or services offered by a merchantassociated with the POS device 610.

As shown by reference number 622 in FIG. 6, POS device 610 determines anissuer institution associated with the portable financial device. Forexample, the account identifier may include a BIN that uniquelyidentifies the issuer institution. As shown by reference number 624, POSdevice 610 determines if at least one electronic service application isassociated with the determined issuer institution. For example, the POSdevice 610 can query a look-up table to identify an electronic serviceapplication associated with the determined issuer institution. If thereis no electronic service application associated with the issuerinstitution, the POS device 610 may proceed directly to attempting toauthorize the payment transaction without modifying the paymenttransaction with an electronic service application.

In reference number 624, the POS device 610 may apply at least one ruleto transaction data associated with the transaction. The at least onerule may define at least one of the following requirements of thetransaction for the electronic service application to be determined foruse in conducting or processing the transaction: transaction amount,transaction date and time, transaction or merchant location, transactioncurrency, transaction data category, type of portable financial device,or any combination thereof. For example, an electronic serviceapplication that automatically enrolls the customer or user in anincentive program, automatically causes a benefit to be transmitted touser device 606 of the customer or user, or automatically credit amerchant loyalty account of the customer or user may require that thetransaction occur at a specific time and/or location.

As shown in reference number 626, the POS device 610 provides aninterface or prompt that requests acceptance from the customer or userto conduct or process the transaction with the determined electronicservice application. For example, the POS device 610 may access or loadthe at least one electronic service application to prompt the customeror user to accept enrollment an incentive program, a benefit to betransmitted to user device 606 of the customer or user, and/or credit ofa merchant loyalty account of the customer or user. In some non-limitingembodiments or aspects, as shown in reference number 628, the POS device610 provides the interface or prompt and/or receives the at least onerule by issuing at least one API call to at least one remote or externalcomputing system associated with the at least one electronic serviceapplication, such as backend system 612, transaction service providersystem 602, or issuer system 604 provides the electronic serviceapplication(s) for automatically enrolling the customer or user in anincentive program, automatically causing a benefit to be transmitted touser device 606 of the customer or user, or automatically crediting amerchant loyalty account of the customer or user. In some non-limitingembodiments or examples, the POS device 610 provides the interface orprompt with a request for additional information from the customer oruser to configure application the electronic service applicationaccording to one or more user preferences. For example, the POS device610 can prompt the customer or user to select a specific incentiveprogram(s), reward(s), and/or benefit(s) for the electronic serviceapplication.

As shown in reference number 630, the POS device 610 receives acceptanceto conduct or process the transaction with the electronic serviceapplication and, if applicable, one or more user preferences, such as aselection of a specific incentive program or reward. If the POS device610 does not receive acceptance to conduct or process the transactionwith the electronic service application, e.g., the customer or userdeclines the request or a timer initiated after sending the acceptancerequest times out, the POS device 610 may proceed directly to attemptingto authorize the payment transaction without modifying the paymenttransaction with the electronic service application. However,non-limiting embodiments and aspects are not limited thereto, andapplication of some electronic service applications may be performedautomatically by the POS device 610 without requesting and/or receivingacceptance from the customer or user.

As shown in reference number 632, in response to theacceptance/preferences shown in reference number 630, the POS device 630modifies the transaction data associated with the transaction to includeat least one of the following: an instruction to automatically enrollthe customer or user in an incentive program(s), an instruction toautomatically cause a benefit to be transmitted to user device 606 ofthe customer or user, or an instruction to automatically credit amerchant loyalty account of the customer or user. For example, the POSdevice 620 may modify the transaction data to include an instruction tothe backend system 612 to automatically credit a merchant loyaltyaccount of the customer or user. The POS device may modify thetransaction data to include an instruction to the transaction providersystem 602 and/or the issuer system 604 to automatically enroll thecustomer or user in an incentive program(s) associated with thetransaction service provider and/or the issuing institution and/or toautomatically transmit a benefit to user device 606 of the customer oruser.

As shown in reference number 634 the POS device 610 transmits anauthorization message request including the modified transaction data totransaction service provider system 502 and issuer system 504 so thatthe payment transaction may be authorized, settled, and/or cleared. Asshown in reference number 636, in response to the authorization requestmessage as shown in reference number 634, the POS device 610 receives anauthorization response message that includes an indication that thepayment transaction was successfully completed (e.g., authorized,cleared, settled, and/or the like) or not successfully completed (e.g.,not authorized, not cleared, not settled, and/or the like) and, ifapplicable, an indication that the customer or user was enrolled in theincentive program(s). As shown in reference number 638, POS device 610may display the indication that the payment transaction was successfullycompleted or not successfully completed and/or the indication that thecustomer or user was enrolled in the incentive program.

As shown in reference number 640, user device 606 may receive a benefittransmitted from the transaction service provider system 602 and/or theissuer instruction 604 as a result of the electronic service applicationbeing applied to the transaction, as described herein. As shown inreference number 642, the POS device 610 may transmit an instruction tothe backend system 612 to credit the merchant loyalty account associatedwith the customer or user in response to completion of the transaction.

Although the disclosure has been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred embodiments, it is to be understood that suchdetail is solely for that purpose and that the disclosure is not limitedto the disclosed embodiments, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any embodiment can be combined with one or morefeatures of any other embodiment.

What is claimed is:
 1. A computer-implemented method for dynamicapplication selection for payment transactions, the method comprising:determining, with at least one processor of a point-of-sale (POS)device, identification data of an issuer institution associated with aportable financial device based at least partially on transaction dataassociated with at least one transaction at a merchant with the portablefinancial device; determining, with the at least one processor of thePOS device, at least one electronic service application of a pluralityof electronic service applications based at least partially on theidentification data of the issuer institution, wherein a plurality ofelectronic service application data associated with the plurality ofelectronic service applications is stored in association with aplurality of issuing institutions at a merchant system of the merchant,and wherein the plurality of electronic service application datacomprises Application Programming Interface (API) information associatedwith the plurality of electronic service applications; initiating, withthe at least one processor of the POS device, at least one API call toat least one external computing system associated with the at least oneelectronic service application to access the at least one electronicservice application at the at least one external computing system;providing, with the at least one processor of the POS device, via adisplay of the POS device, a graphical user interface including a promptto accept the at least one electronic service application for processingthe at least one transaction by accessing, with the at least oneprocessor of the POS device, the at least one electronic serviceapplication at the at least one external computing system; receiving,with the at least one processor of the POS device, via the display ofthe POS device, acceptance data that indicates acceptance of the atleast one electronic service application for processing the at least onetransaction; modifying, with the at least one processor of the POSdevice, the at least one transaction based at least partially on theelectronic service application data associated with the at least oneelectronic service application; communicating, with the at least oneprocessor of the POS device, to an issuer system associated with theissuer institution, an authorization request message associated with theat least one modified transaction; and receiving, with the at least oneprocessor of the POS device, an authorization response message aftercommunicating the authorization request message.
 2. Thecomputer-implemented method of claim 1, wherein the at least oneexternal computing system includes a cloud-based POS system.
 3. Thecomputer-implemented method of claim 1, wherein the plurality ofelectronic service application data is stored on at least one of thefollowing: the POS device, a backend system of the merchant system, orany combination thereof.
 4. The computer-implemented method of claim 1,wherein the issuer institution is associated with two or more electronicservice applications of the plurality of electronic serviceapplications, the method further comprising: based at least partially onthe identification data of the issuer institution, determining, with theat least one processor of the POS device, a subset of the two or moreelectronic service applications as the at least one electronic serviceapplication.
 5. The computer-implemented method of claim 1, furthercomprising: determining, with the at least one processor of the POSdevice, the at least one electronic service application based at leastpartially on at least one of the following: a transaction amount of theat least one transaction, a transaction date and/or time of the at leastone transaction, a location of the at least one transaction or merchant,a currency of the at least one transaction, a transaction data categoryof the at least one transaction, a type of the portable financialdevice, or any combination thereof.
 6. The computer-implemented methodof claim 1, further comprising: receiving, with at least one processorof the POS device, the transaction data associated with the at least onetransaction, wherein the transaction data comprises portable financialdevice data associated with the portable financial device, and whereinthe portable financial device data comprises an account identifier. 7.The computer-implemented method of claim 1, wherein the identificationdata of the issuer institution comprises at least one of the following:a Bank Identification Number (BIN), a range of BINs, an IssuerIdentification Number (IIN), a range of IINs, or any combinationthereof.
 8. The computer-implemented method of claim 1, furthercomprising: transmitting, with the at least one processor of the POSdevice, an instruction to a backend system of the merchant system tocredit a merchant loyalty account associated with a user associated withthe portable financial device.
 9. The computer-implemented method ofclaim 1, wherein modifying the at least one transaction comprises atleast one of the following: reducing a transaction amount of the atleast one transaction; dividing the transaction amount of the at leastone transaction into a plurality of installment amounts; automaticallyenrolling, or causing the enrollment of, a customer associated with theportable financial device in an incentive program; automaticallytransmitting, or causing the transmission of, a benefit to a user deviceof the customer; automatically crediting, or causing the crediting of, amerchant loyalty account of the customer; or any combination thereof.10. A system for dynamic application selection for payment transactions,comprising at least one processor of a point-of-sale (POS) device,wherein the at least one processor of the POS device is programmedand/or configured to: determine identification data of an issuerinstitution associated with a portable financial device based at leastpartially on transaction data associated with at least one transactionat a merchant with the portable financial device; determine at least oneelectronic service application of a plurality of electronic serviceapplications based at least partially on the identification data of theissuer institution, wherein a plurality of electronic serviceapplication data associated with the plurality of electronic serviceapplications is stored in association with a plurality of issuinginstitutions at a merchant system of the merchant, and wherein theplurality of electronic service application data comprises ApplicationProgramming Interface (API) information associated with the plurality ofelectronic service applications; initiate at least one API call to atleast one external computing system associated with the at least oneelectronic service application to access the at least one electronicservice application at the at least one external computing system;provide, via a display of the POS device, a graphical user interfaceincluding a prompt to accept the at least one electronic serviceapplication for processing the at least one transaction by accessing,with the at least one processor of the POS device, the at least oneelectronic service application at the at least one external computingsystem; receive, via the display of the POS device, acceptance data thatindicates acceptance of the at least one electronic service applicationfor processing the at least one transaction; modify the at least onetransaction based at least partially on the electronic serviceapplication data associated with the at least one electronic serviceapplication; communicate to an issuer system associated with the issuerinstitution, an authorization request message associated with the atleast one modified transaction; and receive an authorization responsemessage after communicating the authorization request message.
 11. Thesystem of claim 10, wherein the at least one external computing systemincludes a cloud-based POS system.
 12. The system of claim 10, whereinthe plurality of electronic service application data is stored on atleast one of the following: the POS device, a backend system of themerchant system, or any combination thereof.
 13. The system of claim 10,wherein the issuer institution is associated with two or more electronicservice applications of the plurality of electronic serviceapplications, and wherein the at least one processor of the POS deviceis programmed and/or configured to: based at least partially on theidentification data of the issuer institution, determine a subset of thetwo or more electronic service applications as the at least oneelectronic service application.
 14. The system of claim 10, wherein theat least one processor of the POS device is programmed and/or configuredto: determine the at least one electronic service application based atleast partially on at least one of the following: a transaction amountof the at least one transaction, a transaction date and/or time of theat least one transaction, a location of the at least one transaction ormerchant, a currency of the at least one transaction, a transaction datacategory of the at least one transaction, a type of the portablefinancial device, or any combination thereof.
 15. The system of claim10, wherein the at least one processor of the POS device is programmedand/or configured to: receive the transaction data associated with theat least one transaction, wherein the transaction data comprisesportable financial device data associated with the portable financialdevice, and wherein the portable financial device data comprises anaccount identifier.
 16. The system of claim 10, wherein theidentification data of the issuer institution comprises at least one ofthe following: a Bank Identification Number (BIN), a range of BINs, anIssuer Identification Number (IIN), a range of IINs, or any combinationthereof.
 17. The system of claim 10, wherein the at least one processorof the POS device is programmed and/or configured to: transmit aninstruction to a backend system of the merchant system to credit amerchant loyalty account associated with a user associated with theportable financial device.
 18. The system of claim 10, wherein the atleast one processor of the POS device modifies the at least onetransaction by at least one of the following: reducing a transactionamount of the at least one transaction; dividing the transaction amountof the at least one transaction into a plurality of installment amounts;automatically enrolling, or causing the enrollment of, a customerassociated with the portable financial device in an incentive program;automatically transmitting, or causing the transmission of, a benefit toa user device of the customer; automatically crediting, or causing thecrediting of, a merchant loyalty account of the customer; or anycombination thereof.
 19. A computer program product for dynamicapplication selection for payment transactions, the computer programproduct comprising at least one non-transitory computer-readable mediumincluding program instructions that, when executed by at least oneprocessor of a point-of-sale (POS) device cause the at least oneprocessor of the POS device to: determine identification data of anissuer institution associated with a portable financial device based atleast partially on transaction data associated with at least onetransaction at a merchant with the portable financial device; determineat least one electronic service application of a plurality of electronicservice applications based at least partially on the identification dataof the issuer institution, wherein a plurality of electronic serviceapplication data associated with the plurality of electronic serviceapplications is stored in association with a plurality of issuinginstitutions at a merchant system of the merchant, and wherein theplurality of electronic service application data comprises ApplicationProgramming Interface (API) information associated with the plurality ofelectronic service applications; initiate at least one API call to atleast one external computing system associated with the at least oneelectronic service application to access the at least one electronicservice application at the at least one external computing system;provide, via a display of the POS device, a graphical user interfaceincluding a prompt to accept the at least one electronic serviceapplication for processing the at least one transaction by accessing,with the at least one processor of the POS device, the at least oneelectronic service application at the at least one external computingsystem; receive, via the display of the POS device, acceptance data thatindicates acceptance of the at least one electronic service applicationfor processing the at least one transaction; modify the at least onetransaction based at least partially on the electronic serviceapplication data associated with the at least one electronic serviceapplication; communicate to an issuer system associated with the issuerinstitution, an authorization request message associated with the atleast one modified transaction; and receive an authorization responsemessage after communicating the authorization request message.
 20. Thecomputer program product of claim 19, wherein the at least one externalcomputing system includes a cloud-based POS system.